The task landed in your lap with no brief. No template, no example from last quarter, no one obviously in charge of answering questions about it. Your instinct is to wait until somebody clarifies.
Waiting feels like caution, and it is the option that gets judged hardest later, because the person who assigned it will remember two weeks of silence and nothing else. There is a well-documented version of this problem, and it happened at 2,818 feet.
208 seconds, and no checklist written for it
Three minutes into a routine afternoon departure on January 15, 2009, US Airways Flight 1549 hit a flock of Canada geese two and a half minutes after leaving LaGuardia. Both engines lost thrust. Captain Chesley Sullenberger had 208 seconds.
First Officer Jeff Skiles reached for the dual engine failure checklist, which is exactly what training says to do. The problem is what the NTSB later documented about that checklist: it was built for a failure above 20,000 feet, high enough to work down the list and still recover altitude. Simulator training at the airline ran the scenario at 25,000 feet. The NTSB investigation also noted that low-altitude dual engine failure checklists were not readily available anywhere in the industry, and the ditching checklist assumed one engine was still running, which made it useless here too.
Sit with that. The most procedure-driven profession on earth handed its crew a situation with no applicable procedure. All 155 people on board survived anyway.
Why experts never line up five options
Sullenberger did not invent a solution from nothing, and he did not run a comparison of every possibility either. He considered returning to LaGuardia, then Teterboro, then the Hudson, and took the first one that held up.
The sequence matches what Gary Klein found when his team studied fireground commanders in the 1980s. The commanders insisted they never made decisions, that they just followed procedure, and then admitted the procedure was not written down anywhere. What Klein's team actually observed was this: about 80 percent of decisions were made in under a minute, and in each case one option came to mind quickly, got evaluated on its own, and was acted on if it held. He called it the recognition-primed decision model.
The mechanism transfers directly to your unbriefed task. Under ambiguity, ranking every possible approach is the expensive move, because you cannot rank options against criteria nobody has given you. Generating one workable option and testing it against your constraints costs a fraction as much and produces something real to react to. A second benefit matters more in an office than in a cockpit. A written option pulls information out of people that a question never will. Ask a manager what they want and you get a shrug and a calendar invite for next week. Show that same manager a wrong draft and they will tell you precisely what is wrong with it, usually within the hour, because correcting a specific thing is far easier than describing an abstract one.
Sullenberger described the underlying resource to CBS afterward: "I've been making small, regular deposits in this bank of experience, education, and training. On January 15, the balance was sufficient so that I could make a sudden, large withdrawal."
The 30-minute start
Set a timer. Thirty minutes, one pass, four steps.
Minute 1 to 5. Write the constraint line. One sentence, no more: "This is done when [specific outcome] is true, for [specific person], by [specific date]." If you cannot fill all three brackets, the blank one is your actual question, and it is a far sharper question than "what did you want here?"
Minute 5 to 15. Generate one approach, not a menu. Answer this: if you had to hand something over tomorrow morning, what would you build? Write it in five bullet points. Speed is the point, because the first workable option is what experts under pressure produce.
Minute 15 to 25. Simulate the two failures. Name the two most likely ways this approach gets rejected. Wrong audience. Missing data. Too expensive. Duplicates something another team already shipped. If one of those two is fatal, go back and take the next approach, which costs ten more minutes, not another week. Anything survivable gets written down as a known risk and flagged when you send the work, so nobody discovers it later and assumes you missed it.
Minute 25 to 30. Cut it to the smallest showable version. One slide, one page, one working screen, one paragraph. Something a person can react to in ninety seconds.
Send this before Wednesday
Take the ambiguous thing sitting on your list right now. Do the 30-minute start, then send this exact message to whoever assigned it.
Subject: My working assumption on [task]
Here is what I am assuming this needs to be: [one sentence from your constraint line].
Based on that, here is the approach: [three lines].
Attached is the smallest version so you can see the shape of it.
If I do not hear anything by Thursday at noon, I will keep building on this assumption.
The last sentence is the most important part. A named default deadline converts your silence problem into their decision problem, politely, and gives you permission to move. Managers correct a draft in four minutes. They answer an open-ended question in four days, if at all.
Sullenberger had 208 seconds because the situation gave him 208 seconds. You have a Wednesday, which is a luxury by comparison, and the same rule applies to both: the person who produces a checkable option first is the one everybody else ends up reacting to.
Until next time, Future Leader
